Prerequisites for the Nodinite Web Services Monitoring Agent
Prepare your environment for seamless monitoring of Web Services and Web Applications with Nodinite. This page outlines all prerequisites for installing and running the Web Services Monitoring Agent, ensuring a smooth and secure deployment.
With Nodinite, you can:
- Monitor any Web Service, Web Application, WCF, or Web API
- Deploy agents on-premises or in the cloud, with flexible network options
- Leverage secure Windows authentication and granular user rights
- Automate monitoring with minimal firewall and network configuration
This page describes the prerequisites for installing and running the Nodinite Web Services Monitoring Agent.
This diagram shows how the Nodinite Web Services Monitoring Agent connects to web servers and APIs, managed by the Nodinite Monitoring Service.
You can install agent instances on the same network as Nodinite, or deploy them in the cloud/offsite using Service Bus Relaying. See Microsoft Service Bus Relaying - External Link for more details.
We recommend that you keep this agent close to the Nodinite Server
| Verified | Topic |
|---|---|
| Software Requirements | |
| What Windows User Rights does the Web Services Monitoring agent require? | |
| What Firewall settings are required for the Web Services Monitoring agent? |
Software requirements
| Product | ||
|---|---|---|
| Windows Server | Windows 2025Windows 2022Windows 2019Windows 2016Windows 2012 R2Windows 2012Windows 2008 R2 | |
| .NET Framework | .NET Framework 4.8 or later New 6.0Our recommendation is .NET Framework 4.8.1 or later |
Versions 6.0 and later require .NET Framework 4.8 or later.
Versions 5.4 and later require .NET Framework 4.6.2 or later.
Versions before 5.4 require .NET Framework 4.5.2 or later.
What Windows User Rights does the Web Services Monitoring agent require?
The Web Services Monitoring Agent installs as a Windows Service—usually on the Nodinite application server—and runs with least possible privileges:
- Local named account or domain account (preferred). Follow this guide 'How to set Logon as a Service right' for more information.
You can fine-tune access rights per Web Service/Web Application. Configure these individually—see the Configuration user guide for details.
What Firewall settings are required for the Web Services Monitoring agent?
The Web Services Monitoring agent uses both inbound and outbound communication:
This diagram illustrates the network and firewall communication paths for the Nodinite Web Services Monitoring Agent.
1. TCP Ports between the Monitoring Service and the Web Services Monitoring agent
The following ports must be allowed on the Windows server where the agent is installed and running:
| Port | Name | Inbound | Outbound | TCP | UDP | Comment |
|---|---|---|---|---|---|---|
| 53 | DNS | The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts file) |
And further with 'Option 1' or 'Option 2' as documented next:
Option 1 (Local network)
| Port | Name | Inbound | Outbound | TCP | UDP | Comment |
|---|---|---|---|---|---|---|
| 8000 | RPC | Communication is initiated by the Monitoring Service |
Option 2 (Cloud/Hybrid)
Use Service Bus Relayed connections when Nodinite and the agent are on totally different networks.
Nodinite uses the same principle technique as the On-Premise data gateway, see 'Adjust communication settings for the on-premises data gateway' user guide.
| Port | Name | Inbound | Outbound | TCP | UDP | Comment |
|---|---|---|---|---|---|---|
| 443 | HTTPS | Secure outbound traffic | ||||
| 5671, 5672 | Secure AMQP | |||||
| 9350 - 9354 | Net.TCP |
2. TCP Ports between Nodinite Web Services Monitoring Agent and Web Services
| Port | Name | Inbound | Outbound | TCP | UDP | Comment |
|---|---|---|---|---|---|---|
| 53 | DNS | The Agent needs to know where your other servers/services are (can sometimes optionally be solved with user-defined entries in the hosts file in each Windows server instance), review the following 'Microsoft' user guide |
||||
| 80 | HTTP | default for HTTP | ||||
| 443 | HTTPS | default for HTTPS |
Important
The actual port may depend on user configuration and you must open whatever TCP port your Web Services and Web Applications are using
Frequently asked questions
Find solutions to common problems and FAQs for the Nodinite Web Service Monitoring Agent in the Troubleshooting user guide.
Next Step
Install Web Service Monitoring Agent
Related Topics
Configuration
Add or manage a Monitoring Agent Configuration
Monitoring
Administration